Autogenerated HTML docs for v2.21.0-498-g14c0f8
diff --git a/gitweb.html b/gitweb.html index 5e91b99..ed0e904 100644 --- a/gitweb.html +++ b/gitweb.html
@@ -811,7 +811,7 @@ <h2 id="_configuration">CONFIGURATION</h2> <div class="sectionbody"> <div class="paragraph"><p>Various aspects of gitweb’s behavior can be controlled through the configuration -file <em>gitweb_config.perl</em> or <em>/etc/gitweb.conf</em>. See the <a href="gitweb.conf.html">gitweb.conf(5)</a> +file <code>gitweb_config.perl</code> or <code>/etc/gitweb.conf</code>. See the <a href="gitweb.conf.html">gitweb.conf(5)</a> for details.</p></div> <div class="sect2"> <h3 id="_repositories">Repositories</h3> @@ -824,7 +824,7 @@ <div class="content"> <pre><code>our $projectroot = '/path/to/parent/directory';</code></pre> </div></div> -<div class="paragraph"><p>The default value for <code>$projectroot</code> is <em>/pub/git</em>. You can change it during +<div class="paragraph"><p>The default value for <code>$projectroot</code> is <code>/pub/git</code>. You can change it during building gitweb via <code>GITWEB_PROJECTROOT</code> build configuration variable.</p></div> <div class="paragraph"><p>By default all Git repositories under <code>$projectroot</code> are visible and available to gitweb. The list of projects is generated by default by scanning the @@ -1038,7 +1038,7 @@ <pre><code>Unnamed repository; edit this file to name it for gitweb.</code></pre> </div></div> <div class="paragraph"><p>from the template during repository creation, usually installed in -<em>/usr/share/git-core/templates/</em>. You can use the <code>gitweb.description</code> repo +<code>/usr/share/git-core/templates/</code>. You can use the <code>gitweb.description</code> repo configuration variable, but the file takes precedence.</p></div> </dd> <dt class="hdlist1"> @@ -1336,7 +1336,7 @@ <div class="sect2"> <h3 id="_apache_as_cgi">Apache as CGI</h3> <div class="paragraph"><p>Apache must be configured to support CGI scripts in the directory in -which gitweb is installed. Let’s assume that it is <em>/var/www/cgi-bin</em> +which gitweb is installed. Let’s assume that it is <code>/var/www/cgi-bin</code> directory.</p></div> <div class="listingblock"> <div class="content"> @@ -1360,7 +1360,7 @@ <div class="paragraph"><p>You can use mod_perl with gitweb. You must install Apache::Registry (for mod_perl 1.x) or ModPerl::Registry (for mod_perl 2.x) to enable this support.</p></div> -<div class="paragraph"><p>Assuming that gitweb is installed to <em>/var/www/perl</em>, the following +<div class="paragraph"><p>Assuming that gitweb is installed to <code>/var/www/perl</code>, the following Apache configuration (for mod_perl 2.x) is suitable.</p></div> <div class="listingblock"> <div class="content"> @@ -1386,7 +1386,7 @@ <h3 id="_apache_with_fastcgi">Apache with FastCGI</h3> <div class="paragraph"><p>Gitweb works with Apache and FastCGI. First you need to rename, copy or symlink gitweb.cgi to gitweb.fcgi. Let’s assume that gitweb is -installed in <em>/usr/share/gitweb</em> directory. The following Apache +installed in <code>/usr/share/gitweb</code> directory. The following Apache configuration is suitable (UNTESTED!)</p></div> <div class="listingblock"> <div class="content"> @@ -1434,20 +1434,20 @@ </VirtualHost></code></pre> </div></div> <div class="paragraph"><p>The above configuration expects your public repositories to live under -<em>/pub/git</em> and will serve them as <code>http://git.domain.org/dir-under-pub-git</code>, +<code>/pub/git</code> and will serve them as <code>http://git.domain.org/dir-under-pub-git</code>, both as clonable Git URL and as browseable gitweb interface. If you then start your <a href="git-daemon.html">git-daemon(1)</a> with <code>--base-path=/pub/git --export-all</code> then you can even use the <code>git://</code> URL with exactly the same path.</p></div> <div class="paragraph"><p>Setting the environment variable <code>GITWEB_CONFIG</code> will tell gitweb to use the -named file (i.e. in this example <em>/etc/gitweb.conf</em>) as a configuration for +named file (i.e. in this example <code>/etc/gitweb.conf</code>) as a configuration for gitweb. You don’t really need it in above example; it is required only if your configuration file is in different place than built-in (during -compiling gitweb) <em>gitweb_config.perl</em> or <em>/etc/gitweb.conf</em>. See +compiling gitweb) <em>gitweb_config.perl</em> or <code>/etc/gitweb.conf</code>. See <a href="gitweb.conf.html">gitweb.conf(5)</a> for details, especially information about precedence rules.</p></div> <div class="paragraph"><p>If you use the rewrite rules from the example you <strong>might</strong> also need something like the following in your gitweb configuration file -(<em>/etc/gitweb.conf</em> following example):</p></div> +(<code>/etc/gitweb.conf</code> following example):</p></div> <div class="listingblock"> <div class="content"> <pre><code>@stylesheets = ("/some/absolute/path/gitweb.css"); @@ -1503,7 +1503,7 @@ </div></div> <div class="paragraph"><p>Here actual project root is passed to gitweb via <code>GITWEB_PROJECT_ROOT</code> environment variable from a web server, so you need to put the following -line in gitweb configuration file (<em>/etc/gitweb.conf</em> in above example):</p></div> +line in gitweb configuration file (<code>/etc/gitweb.conf</code> in above example):</p></div> <div class="listingblock"> <div class="content"> <pre><code>$projectroot = $ENV{'GITWEB_PROJECTROOT'} || "/pub/git";</code></pre> @@ -1513,7 +1513,7 @@ referenced by <code>$per_request_config</code>;</p></div> <div class="paragraph"><p>These configurations enable two things. First, each unix user (<code><user></code>) of the server will be able to browse through gitweb Git repositories found in -<em>~/public_git/</em> with the following url:</p></div> +<code>~/public_git/</code> with the following url:</p></div> <div class="literalblock"> <div class="content"> <pre><code>http://git.example.org/~<user>/</code></pre> @@ -1523,7 +1523,7 @@ <div class="paragraph"><p>If you already use ‘mod_userdir` in your virtual host or you don’t want to use the '~’ as first character, just comment or remove the second rewrite rule, and uncomment one of the following according to what you want.</p></div> -<div class="paragraph"><p>Second, repositories found in <em>/pub/scm/</em> and <em>/var/git/</em> will be accessible +<div class="paragraph"><p>Second, repositories found in <code>/pub/scm/</code> and <code>/var/git/</code> will be accessible through <code>http://git.example.org/scm/</code> and <code>http://git.example.org/var/</code>. You can add as many project roots as you want by adding rewrite rules like the third and the fourth.</p></div> @@ -1542,7 +1542,7 @@ <pre><code>http://git.example.com/project.git/shortlog/sometag</code></pre> </div></div> <div class="paragraph"><p>i.e. without <em>gitweb.cgi</em> part, by using a configuration such as the -following. This configuration assumes that <em>/var/www/gitweb</em> is the +following. This configuration assumes that <code>/var/www/gitweb</code> is the DocumentRoot of your webserver, contains the gitweb.cgi script and complementary static files (stylesheet, favicon, JavaScript):</p></div> <div class="listingblock"> @@ -1572,9 +1572,9 @@ <code>@stylesheets</code>, <code>$my_uri</code> and <code>$home_link</code>, but you lose "dumb client" access to your project .git dirs (described in "Single URL for gitweb and for fetching" section). A possible workaround for the latter is the -following: in your project root dir (e.g. <em>/pub/git</em>) have the projects -named <strong>without</strong> a .git extension (e.g. <em>/pub/git/project</em> instead of -<em>/pub/git/project.git</em>) and configure Apache as follows:</p></div> +following: in your project root dir (e.g. <code>/pub/git</code>) have the projects +named <strong>without</strong> a .git extension (e.g. <code>/pub/git/project</code> instead of +<code>/pub/git/project.git</code>) and configure Apache as follows:</p></div> <div class="listingblock"> <div class="content"> <pre><code><VirtualHost *:80> @@ -1609,7 +1609,7 @@ </div></div> <div class="paragraph"><p>will provide human-friendly gitweb access.</p></div> <div class="paragraph"><p>This solution is not 100% bulletproof, in the sense that if some project has -a named ref (branch, tag) starting with <em>git/</em>, then paths such as</p></div> +a named ref (branch, tag) starting with <code>git/</code>, then paths such as</p></div> <div class="literalblock"> <div class="content"> <pre><code>http://git.example.com/project/command/abranch..git/abranch</code></pre> @@ -1629,7 +1629,7 @@ <h2 id="_see_also">SEE ALSO</h2> <div class="sectionbody"> <div class="paragraph"><p><a href="gitweb.conf.html">gitweb.conf(5)</a>, <a href="git-instaweb.html">git-instaweb(1)</a></p></div> -<div class="paragraph"><p><em>gitweb/README</em>, <em>gitweb/INSTALL</em></p></div> +<div class="paragraph"><p><code>gitweb/README</code>, <code>gitweb/INSTALL</code></p></div> </div> </div> <div class="sect1"> @@ -1643,7 +1643,7 @@ <div id="footer"> <div id="footer-text"> Last updated - 2018-01-27 08:11:04 JST + 2019-04-22 12:35:42 JST </div> </div> </body> 